Skip to content
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.

Migrate k8s autodiscovery pipeline #3596

Merged
merged 5 commits into from
Aug 2, 2023

Conversation

reakaleek
Copy link
Member

@reakaleek reakaleek commented Jul 27, 2023

What does this PR do?

Migrate k8s autodiscovery pipeline to GitHub Actions workflow.

Why is it important?

Jenkins Migration

How to test?

Workflow run: https://github.com/elastic/e2e-testing/actions/runs/5689630212/job/15421501777?pr=3596

Author's Checklist

  • Create workflow that runs k8s-autodiscover test
  • Remove deprecated Jenkins configs

@mergify
Copy link
Contributor

mergify bot commented Jul 27, 2023

This pull request does not have a backport label. Could you fix it @reakaleek? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit
    NOTE: backport-skip has been added to this pull request.

@mergify mergify bot added the backport-skip Skip notification from the automated backport with mergify label Jul 27, 2023
@elasticmachine
Copy link
Contributor

elasticmachine commented Jul 27, 2023

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-07-31T12:30:03.807+0000

  • Duration: 18 min 21 sec

Steps errors 3

Expand to view the steps failures

Setup Stack node
  • Took 10 min 39 sec . View more details here
  • Description: make -C .ci create-stack
Setup Stack node
  • Took 3 min 1 sec . View more details here
  • Description: make -C .ci create-stack
Setup Stack node
  • Took 3 min 1 sec . View more details here
  • Description: make -C .ci create-stack

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@reakaleek reakaleek force-pushed the feature/migrate-k8s-autodiscovery-pipeline branch 3 times, most recently from f796ab3 to 2fdd38c Compare July 27, 2023 22:20
@reakaleek reakaleek force-pushed the feature/migrate-k8s-autodiscovery-pipeline branch from 2fdd38c to 6f565d2 Compare July 28, 2023 07:57
@reakaleek reakaleek self-assigned this Jul 28, 2023
@reakaleek reakaleek requested review from adam-stokes and a team July 28, 2023 08:02
@reakaleek reakaleek marked this pull request as ready for review July 28, 2023 08:03
@reakaleek reakaleek marked this pull request as draft July 28, 2023 08:10
@reakaleek reakaleek added the backport-v7.17.0 Automated backport with mergify label Jul 28, 2023
@mergify mergify bot removed the backport-skip Skip notification from the automated backport with mergify label Jul 28, 2023
@reakaleek reakaleek added backport-skip Skip notification from the automated backport with mergify backport-v8.8.0 Automated backport with mergify backport-v8.9.0 Automated backport with mergify and removed backport-skip Skip notification from the automated backport with mergify labels Jul 28, 2023
@reakaleek reakaleek marked this pull request as ready for review July 28, 2023 08:16
run: echo "version=$(cat .go-version)" >> "$GITHUB_OUTPUT"
- uses: actions/setup-go@v4
with:
go-version: ${{ steps.get-go-version.outputs.version }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

@reakaleek reakaleek Jul 31, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was considering this.

But the version defined in

go 1.14

differs from the version defined in

and according to the docs it only accepts paths to go.mod or go.work files. Hence, I was not able to use .go-version file.

@kuisathaverat
Copy link
Contributor

@cachedout I think we should start removing all the stuff is not used in this repo to avoid confusion in the future. Of course in a follow up PR.

@cachedout
Copy link
Contributor

@kuisathaverat Indeed. Ultimately, I'd like to archive the entire thing to be honest with you. IMHO we should file a follow-up issue to migrate the k8s autodiscovery tests to a new testing framework and at that point, there should be no reason to keep this repo along any longer. WDYT?

@reakaleek reakaleek requested a review from amannocci July 31, 2023 09:20
@reakaleek reakaleek merged commit 37e80f6 into main Aug 2, 2023
3 of 5 checks passed
@reakaleek reakaleek deleted the feature/migrate-k8s-autodiscovery-pipeline branch August 2, 2023 11:50
mergify bot pushed a commit that referenced this pull request Aug 2, 2023
* Migrate k8s-autodiscovery test to GH Actions workflow

* Remove Jenkins jobs

* Test stack snapshot branches

* Use sha for action version

* empty

(cherry picked from commit 37e80f6)

# Conflicts:
#	.ci/jobs/e2e-testing-k8s-autodiscovery-daily-mbp.yml
#	.github/workflows/opentelemetry.yml
mergify bot pushed a commit that referenced this pull request Aug 2, 2023
* Migrate k8s-autodiscovery test to GH Actions workflow

* Remove Jenkins jobs

* Test stack snapshot branches

* Use sha for action version

* empty

(cherry picked from commit 37e80f6)
mergify bot pushed a commit that referenced this pull request Aug 2, 2023
* Migrate k8s-autodiscovery test to GH Actions workflow

* Remove Jenkins jobs

* Test stack snapshot branches

* Use sha for action version

* empty

(cherry picked from commit 37e80f6)
reakaleek added a commit that referenced this pull request Aug 2, 2023
* Migrate k8s-autodiscovery test to GH Actions workflow

* Remove Jenkins jobs

* Test stack snapshot branches

* Use sha for action version

* empty

(cherry picked from commit 37e80f6)

Co-authored-by: Jan Calanog <[email protected]>
reakaleek added a commit that referenced this pull request Aug 2, 2023
* Migrate k8s autodiscovery pipeline (#3596)

* Migrate k8s-autodiscovery test to GH Actions workflow

* Remove Jenkins jobs

* Test stack snapshot branches

* Use sha for action version

* empty

(cherry picked from commit 37e80f6)

# Conflicts:
#	.ci/jobs/e2e-testing-k8s-autodiscovery-daily-mbp.yml
#	.github/workflows/opentelemetry.yml

* Fix conflicts

---------

Co-authored-by: Jan Calanog <[email protected]>
reakaleek added a commit that referenced this pull request Aug 2, 2023
* Migrate k8s-autodiscovery test to GH Actions workflow

* Remove Jenkins jobs

* Test stack snapshot branches

* Use sha for action version

* empty

(cherry picked from commit 37e80f6)

Co-authored-by: Jan Calanog <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport-v7.17.0 Automated backport with mergify backport-v8.8.0 Automated backport with mergify backport-v8.9.0 Automated backport with mergify
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants